The objective of this activity is to get a clear understanding of the applications that are used and the data streams that are in use in the defined scope of the assignement. In the current state the focus will be on a high level overview.

By mapping the earlier defined high level processes on the Application Landscape a good view on the applications in scope and the way they are related to each other is generated. Furtermore it helps to identify duplicate functionality if a process is run on more than one application. It helps to identify duplicate storage (central, decentral) of information. These steps also help to identify whether the scope is chosen correctly.

The scope of this method ends here, that means that aspects as infrastructure, security et cetera are out of scope. In case these elements have to be dealed with methods like Integrated Architecture Framework can be used.

Purpose is to answer the following questions:

• What does the current application landscape look like?
• What business services are supported by the application landscape?
• Which interfaces are in place between the applications (internal and external)?
• The flow of the data between the applications?

This activity is optional depending on the agreed scope and approach in Focus and Direction. If in the Focus and Direction it has been agreed that the Application Landscape is in scope this activity will be executed. Most of the time a (technical) architect will participate in this. As mentioned earlier, the level of granularity is determined and should be taken into account.

If this activity is performed after the Information Usage activity it is mainly concerned with identifying the application landscape that is in scope. This is done by mapping the data used by the processes on the data interaction of the applications. The deliverable will be the current state application landscape.

If the client has limited documentation of the processes this activity can be the starting point of the current state situation. The existing application landscape is the starting point for identifying the information, current process view and business context.

The application mapping can be useful for spotting duplicate functionality and data. The mapping is done by mapping the data used by the processes on the data interaction of the applications.

Data flow diagram (at application level). See figure below for example.